{extend name="base/base" /}
{block name="head"}{__block__}{/block}
{block name="others"}

<style>
.texts:hover {background:#d5d8d5; color:#000;}
</style>


    <style>
        a {
            color: #337ab7;
        }
        .botom-content-wrap {
            margin-bottom: 40px;
        }
        .wenz-left {
            width: 14%;
            background: #ffffff;
            height: 100vh;
            border-radius: 4px;
            padding: 0 10px;
            box-sizing: border-box;
        }
        .wenz-left .wenz-text {
            color: #000000;
            height: 46px;
            line-height: 46px;
            border-bottom: 1px solid #f0f6fb;
            font-size: 18px;
        }
        .wenz-left .wenz-list-content {
            width: 100%;
            padding-top: 10px;
        }
        .wenz-left .wenz-list-content .texts {
            font-size: 14px;
            margin-bottom: 20px;
            cursor: pointer;
			border-bottom:1px solid;
			padding-bottom:10px;
        }
        .wenz-right {
            width: 85%;
            height: 100vh;
            overflow-y: auto;
            background: #ffffff;
            border-radius: 4px;
            padding: 0 10px;
            box-sizing: border-box;
        }
        .wenz-right .right-title {
            width: 100%;
            height: 74px;
            font-size: 28px;
            color: #000000;
            font-weight: bold;
            border-bottom: 1px solid #e2e8f0;
            margin-bottom: 30px;
        }
        .wenz-right .right-titles {
            width: 100%;
            height: 40px;
            font-size: 22px;
            color: #000000;
            font-weight: bold;
            border-bottom: 1px solid #e2e8f0;
            margin-bottom: 30px;
        }
        .wenz-right .right-titless {
            width: 100%;
            font-size: 16px;
            color: #000000;
            margin-bottom: 20px;
        }
        .wenz-right .abs-och {
            width: 100%;
            margin-bottom: 28px;
        }
        .wenz-right .abs-och {
            width: 100%;
            border-left: 4px solid #e2e8f0;
            padding-left: 16px;
        }
        .wenz-right .abs-och .nameaa {
            color: #6a737d;
            margin-bottom: 28px;
            font-size: 14px;
        }
        .wenz-right .a-bq {
            margin-bottom: 12px;
            font-size: 16px;
        }
        @media screen and (max-width:822px){
            .wenz-left{
                display: block;
				width: 30%;
            }
            .wenz-right {
                width: 70%;
            }
			.wenz-left .wenz-text{
				height:auto;
			}
        }
		th{
		    text-align: center;
			border: 1px solid;
		}
		td{
		    text-align: center;
			border: 1px solid;
		}		
    </style>
{/block}
{block name="header"}{__block__}{/block}
{block name="body"}
    <div class="botom-content-wrap flex-top">
        <div class="wenz-left">
            <div class="wenz-text">Docs</div>
            <div class="wenz-list-content">
                <div class="texts" @click="docselectIx = 0">1. Check hardware requirements</div>
                <div class="texts" @click="docselectIx = 1">2. Check the pre-requisite environment</div>
                <div class="texts" @click="docselectIx = 2">3. Deploy software nodes</div>
                <div class="texts" @click="docselectIx = 3">4. Start the mining program</div>
                <div class="texts" @click="docselectIx = 4">5. Technology roadmap</div>
                <div class="texts" @click="docselectIx = 5">6. Rules of allocation of World Database blocks</div>
                <div class="texts" @click="docselectIx = 6">7. Design architecture of the project</div>
                <div class="texts" @click="docselectIx = 7">8. Disclaimer</div>
            </div>
        </div>
		
        <div class="wenz-right" v-show="docselectIx == 0">
            <div style="margin-left: 10px;">				
                <div class="right-title flex-l">Hardware requirements</div>
                <div class="right-titles flex-l">Nodes</div>
				<div>
					<p>Installed on macOS or Linux. Windows is not currently supported.</p>
					<p>8-core CPU and 32 GB of RAM. Models with Intel® SHA Extensions (AMD Zen or higher microarchitecture, or Intel Ice Lake or higher) will run much faster.</p>
					<p>Enough space for storage (preferably on an SSD). The chain is growing at a rate of about 12GB per week.</p>
				</div>
				<div class="right-titles flex-l">Miners</div>
				<div>
					<div class="right-titless flex-l">Processor-CPU</div>
					<p>A minimum of 8-core CPU</p>
					
					<div class="right-titless flex-l">Memory-RAM</div>
					<p>A minimum of 128G</p>
					
					<div class="right-titless flex-l">Graphics card - GPU</div>
					<p>A high performance graphics card is recommended, and the following has been tested.</p>
						<table role="table">
						<thead>
						<tr>
						<th>Device Name</th>
						<th>Cores</th>
						</tr>
						</thead>
						<tbody>
						<tr>
						<td>Quadro RTX 6000</td>
						<td>4608</td>
						</tr>
						<tr>
						<td>TITAN RTX</td>
						<td>4608</td>
						</tr>
						<tr>
						<td>Tesla V100</td>
						<td>5120</td>
						</tr>
						<tr>
						<td>Tesla P100</td>
						<td>3584</td>
						</tr>
						<tr>
						<td>Tesla T4</td>
						<td>2560</td>
						</tr>
						<tr>
						<td>Quadro M5000</td>
						<td>2048</td>
						</tr>
						<tr>
						<td>GeForce RTX 3090</td>
						<td>10496</td>
						</tr>
						<tr>
						<td>GeForce RTX 3080</td>
						<td>8704</td>
						</tr>
						<tr>
						<td>GeForce RTX 3070</td>
						<td>5888</td>
						</tr>
						<tr>
						<td>GeForce RTX 2080 Ti</td>
						<td>4352</td>
						</tr>
						<tr>
						<td>GeForce RTX 2080 SUPER</td>
						<td>3072</td>
						</tr>
						<tr>
						<td>GeForce RTX 2080</td>
						<td>2944</td>
						</tr>
						<tr>
						<td>GeForce RTX 2070 SUPER</td>
						<td>2560</td>
						</tr>
						<tr>
						<td>GeForce GTX 1080 Ti</td>
						<td>3584</td>
						</tr>
						<tr>
						<td>GeForce GTX 1080</td>
						<td>2560</td>
						</tr>
						<tr>
						<td>GeForce GTX 2060</td>
						<td>1920</td>
						</tr>
						<tr>
						<td>GeForce GTX 1660 Ti</td>
						<td>1536</td>
						</tr>
						<tr>
						<td>GeForce GTX 1060</td>
						<td>1280</td>
						</tr>
						<tr>
						<td>GeForce GTX 1650 SUPER</td>
						<td>1280</td>
						</tr>
						<tr>
						<td>GeForce GTX 1650</td>
						<td>896</td>
						</tr>
						</tbody>
						</table>
					
					</br>
					
					<div class="right-titless flex-l">Hard disk-Disk</div>
					<p>1TB+ NVME hard disk for cache and storage, and additional hard drives are required for file storage.</p>
					<div class="right-titless flex-l">Process for miners</div>
						<table role="table">
						<thead>
						<tr>
						<th align="center">Operation</th>
						<th align="center">CPU usage</th>
						<th align="center">GPU usage</th>
						<th align="center">Memory (32GiB sectors)</th>
						<th align="center">Remarks</th>
						</tr>
						</thead>
						<tbody>
						<tr>
						<td align="center">Seal: pre-commit Phase 1</td>
						<td align="center">Yes (1 Core or 1 Core-Complex)</td>
						<td align="center">No</td>
						<td align="center">128GiB</td>
						<td align="center">PoRep SDR encoding. Not suitable for parallelization. Core usage depends on the value of FIL_PROOFS_USE_MULTICORE_SDR (opens new window).</td>
						</tr>
						<tr>
						<td align="center">Seal: preCommit Phase 2</td>
						<td align="center">Yes (all cores when no GPU is available)</td>
						<td align="center">Yes</td>
						<td align="center">128GiB</td>
						<td align="center">Uses the Poseidon hashing algorithm to generate Merkle trees. Slower when only CPU is available.</td>
						</tr>
						<tr>
						<td align="center">Seal: commit Phase 1</td>
						<td align="center">Yes (all core)</td>
						<td align="center">No</td>
						<td align="center">-</td>
						<td align="center"></td>
						</tr>
						<tr>
						<td align="center">Seal: commit Phase 2</td>
						<td align="center">Yes (all cores when no GPU is available)</td>
						<td align="center">Yes</td>
						<td align="center">~ 192GiB</td>
						<td align="center">Slower when only CPU is available.</td>
						</tr>
						<tr>
						<td align="center">Unpacking</td>
						<td align="center">Yes (1 core)</td>
						<td align="center">No</td>
						<td align="center">128GiB</td>
						<td align="center"></td>
						</tr>
						<tr>
						<td align="center">Proof of WindowPoSt</td>
						<td align="center">Yes (all cores when no GPU is available)</td>
						<td align="center">Yes</td>
						<td align="center">-</td>
						<td align="center">WindowPoSts must be submitted within 30 minutes. When there are no GPUs available, the more CPUs, the faster.</td>
						</tr>
						<tr>
						<td align="center">Proof of WinningPoSt</td>
						<td align="center">Yes</td>
						<td align="center">No</td>
						<td align="center">-</td>
						<td align="center">WinningPoSt is a less intensive calculation. It must be completed within 25 seconds.</td>
						</tr>
						</tbody>
						</table>
					
				</div>
            </div>
        </div>
		
		
        <div class="wenz-right" v-show="docselectIx == 1">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Operating environment</div>
				
                <div class="right-titles flex-l">Recommended environment</div>
				<div class="abs-och">
					<div><a href="https://ubuntu.com/#download" target="_blank">Ubuntu 18.04</a></div>
				</div>
                <div class="right-titles flex-l">Windows optional Virtual machine</div>
				<div class="abs-och">
					<div><a href="https://www.virtualbox.org/wiki/Downloads" target="_blank">virtualbox</a></div>
				</div>


                <div class="right-titles flex-l">Pre-requisites</div>
				<div class="abs-och">
					<div>apt install mesa-opencl-icd ocl-icd-opencl-dev gcc git bzr jq pkg-config curl clang build-essential hwloc libhwloc-dev wget -y && sudo apt upgrade -y</div>
				</div>

                <div class="right-titles flex-l">Rust</div>
				<div class="abs-och">
					<div>
						<p>curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh</p>
						<p>source $HOME/.cargo/env</p>
					</div>
				</div>
				
				
                <div class="right-titles flex-l">Non-compiled version requirements</div>
				<div class="abs-och">
					<div>
					<p>wget -c https://golang.org/dl/go1.15.5.linux-amd64.tar.gz -O - | sudo tar -xz -C /usr/local</p>
					<p>export PATH=$PATH:/usr/local/go/bin</p>
					</div>
				</div>
            </div>
        </div>
		
		
        <div class="wenz-right" v-show="docselectIx == 2">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Deployment node</div>
				
                <div class="right-titles flex-l">Installation</div>
				<div class="abs-och">
					<div>
					<p>cd /</p>
					<p>wget https://worlddb.s3.amazonaws.com/WD512.zip</p>
					<p>apt install unzip -y</p>
					<p>unzip WD512.zip</p>
					<p>chmod -R 777 wd512</p>
					<!--
					<p>rm ~/go/pkg/mod/github.com/filecoin-project/specs-actors -rf</p>
					<p>rm ~/go/pkg/mod/github.com/filecoin-project/specs-actors@v0.9.13/ -rf</p>
					<p>mkdir -p ~/go/pkg/mod/github.com/filecoin-project/</p>
					<p>cp -r wd-change/specs-actors ~/go/pkg/mod/github.com/filecoin-project/</p>
					<p>cp -r wd-change/specs-actors@v0.9.13 ~/go/pkg/mod/github.com/filecoin-project/</p>
					<p>cd wd512</p>
					<p>make 2k</p>-->
					</div>
				</div>


                <div class="right-titles flex-l">Environment variable configuration</div>
				<div class="abs-och">
					<div>
					<p>source $HOME/.cargo/env</p>
					<p>export RUSTFLAGS="-C target-cpu=native -g"</p>
					</div>
				</div>

                <div class="right-titles flex-l">Optional multi-window</div>
				<div class="abs-och">
					<div>
					<p>apt install screen</p>
					</div>
				</div>
				
                <div class="right-titles flex-l">Configuration in China</div>
				<div class="abs-och">
					<div>
					<p>export IPFS_GATEWAY=https://proof-parameters.s3.cn-south-1.jdcloud-oss.com/ipfs/</p>
					</div>
				</div>
				
                <div class="right-titles flex-l">Installed purge data</div>
				<div class="abs-och">
					<div>
					<p>rm -rf ~/.lotus/</p>
					<p>rm -rf ~/.lotusminer/</p>
					</div>
				</div>
            </div>
        </div>
		
		
        <div class="wenz-right" v-show="docselectIx == 3">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Mining instructions</div>
				
                <div class="right-titles flex-l">Run node (based on test network)</div>
				
				<div class="right-titless flex-l">Run in new window</div>
				
				<div class="abs-och">
					<div>
					<p>screen -S daemon</p>
					<p>cd /wd512</p>
					<p>./lotus daemon --genesis=dev.gen --bootstrap=false</p>
					</div>
				</div>
				
				
				<div class="right-titless flex-l">Return to main window</div>
				<div class="abs-och">
					<div>
					<p>CTRL+A</p>
					<p>CTRL+D</p>
					<p>screen -ls Query all running windows</p>
					<p>screen -r Window name Restoring window</p>
					</div>
				</div>
				
				<div class="abs-och">
					<div>
					<p>Choose One IP Connection</p>
					<p>IP:18.130.175.35  port:43087 sign:12D3KooWMnQP8A3FBAvGWaswrTWmk4npCWbmAThe3kkMZ3NVB4FV</p>
					<p>IP:27.124.46.138  port:36197 sign:12D3KooWMU1vTeQeDcfw4FFmedMQ5j5BS9UJaHpPxgdUoFRUKenC</p>
					</div>
				</div>
				
				<div class="abs-och">
					<div>
					<p>./lotus net connect /ip4/[ip]/tcp/[port]/p2p/[sign]</p>
					</div>
				</div>




				
                <div class="right-titles flex-l">Create a wallet</div>
				<div class="abs-och">
					<div>
					<p>./lotus wallet new bls</p>
					</div>
				</div>

                <div class="right-titles flex-l">Request pledged coins</div>
				<div class="abs-och">
					<div>
					<div><a href="https://hose.worlddb.io/" target="_blank">Get test coins</a></div>
					</div>
				</div>
				
                <div class="right-titles flex-l">Run Miner,Get miner id</div>
				<div class="abs-och">
					<div>
					<p>./lotus-miner init --owner=[Wallet address] --sector-size=512MiB --no-local-storage --nosync</p>
					</div>
				</div>
				
				<div class="right-titless flex-l">Run in new window</div>
				<div class="abs-och">
					<div>
					<p>screen -S miner</p>
					<p>cd /wd512</p>
					<p>./lotus-miner run --nosync</p>
					</div>
				</div>
				
				<div class="right-titless flex-l">Return to main window</div>
				
				
				<div class="right-titles flex-l">Set package temporary directory and seal to final storage directory</div>
				
				<div class="abs-och">
					<div>
					<p>./lotus-miner storage attach --init --seal ~/wd512/s1</p>
					<p>./lotus-miner storage attach --init --seal ~/wd512/s1</p>
					</div>
				</div>
				
				
				
                <div class="right-titles flex-l">Send file request</div>
				<div class="abs-och">
					<div>
					<p>./lotus client import File</p>
					<p>./lotus client deal [File id] [Miner id] 0.0000001 518400</p>
					<p>./lotus client list-deals</p>
					</div>
				</div>
            </div>
        </div>
		
		
		
        <div class="wenz-right" v-show="docselectIx == 4">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Technology roadmap</div>
				
<div class="markdown-body">
                <p>Phase 1 Technology Validation and Research of WorldDatabase  (as of the fourth quarter in 2019)</p>
<p>Deeply studying the technical framework of each public chain and protocol layer of blockchain, the core team read a lot of code and papers (see Appendix) to argue the computation and storage model of massive data in permissionless environment. They demonstrated the combination of OAS business model and token economy, and completed the deduction of theoretical architecture.</p>
<p>Phase 2 Technology demonstration and research of WorldDatabase (January, February, March in 2020)</p>
<p>Select the appropriate blockchain consensus mechanism, determine the high-speed chain design using the Sharding scheme, and the HoneyBadgerBFT consensus algorithm for sub-chains determine the multi-subchain design using Request and Reponse for separate bookkeeping. Refine the structural design for the separation of chain-bank structure. Determine the technical route and technical solution using data holding proof of PDP and access control and encryption mechanism of ABE. Complete the technical white paper version 1.0.</p>
<p>Phase 3 Development of WorldDatabase core components (April, June, August in 2020)</p>
<p>Evaluate and test the performance of libp2p and devp2p, modify the code to implement the underlying data block storage system. Closed source development of WorldDatabase Chain Technical validation of WorldDatabase FS. Community development and real-time open source implementation of WorldDatabase FS based on WorldDatabase FS.  Develop WorldDatabase Agent based on hotspot language to facilitate integration with existing applications.</p>
<p>Phase 4 Development of WorldDatabase Chain Test Network (January, March, June in 2021)</p>
<p>Development of P2P network is used for synchronization of blockchain ledger as well as synchronization of stored data,  virtual machine development and development of built-in contracts and interface of verification API, RPC interface, command line, peripheral tools development. WD's Genesis block was mined for output Open Source WorldDatabase Chain</p>
<p>Phase 5 Test network construction and the development of paradigm based on WorldDatabase (August, October, December in 2021)</p>
<p>Build a large-scale test network based on the community and conduct a comprehensive test. Distribute WDs to encourage early community enthusiasts to develop the example based on WorldDatabase-based applications and test and fix for security and business vulnerabilities in the sample based on the test network.</p>
<p>Phase 6 Expansion of other data service capabilities and data transactions (the first quarter and third quarter in 2022)</p>
<p>Initiated by the Foundation to encourage more database types and service capabilities to be accessed, the World Database ecology explores the capability of data trading based on the ecology.</p>

              </div>
				
				
            </div>
        </div>
		
		
        <div class="wenz-right" v-show="docselectIx == 5">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Rules of allocation of World Database blocks</div>
				
<div class="markdown-body">
                <p>Total quantity: The total quantity of WD is the 200 million</p>
<p>Circulation: 500,000 Genesis blocks are used for the building of initial mining pool.</p>
<p>Mining: 199.5 million pieces are used for mining rewards, with daily production declining linearly and production halving every 3 years [see copy file: The overview of WD mining cycle].</p>
<p>Pledge: Verifiers and nominees need to pledge WD [see copy file: The overview of WD mining cycle].</p>
<p>Destruction: consuming GAS fees, node penalties, etc., all for permanent destruction by burning [see copy file: The overview of WD mining cycle].</p>
<p>Rent: Users who rent the World Database in the cloud need to purchase WD for payment.</p>
<p>Trading: When trading data in Marketplace, the trading party needs to purchase WD for payment.</p>
<p>Rules: 500,000 Genesis blocks are allocated according to the following rules.
10% for airdrop in global community,
30% for creation of mining pool by protocol lab,
60% for creation of mining pool by WD Foundation,
investors and other institutions.[See copy file ( The overview of WD mining cycle ) for process of creating the mining pool.)</p>

              </div>
				
				
            </div>
        </div>
		
        <div class="wenz-right" v-show="docselectIx == 6">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Design architecture of the project</div>
				
<div class="markdown-body">
                <p>World Database is a high-speed, secure and scalable blockchain infrastructure project that can handle millions of transactions per second through sharding technology, providing infinitely scalable storage capacity for Dapp through a secure decentralised cloud database. world Database is made up of the following components, which are.</p>
<p>-a homogeneous multi-chain chain system, World Database Chain, providing high TPS access, Turing-complete smart contracts, cross-chain transaction capabilities, etc.</p>
<p>-A p2p network system, World Database p2p, providing network layer addressing capabilities.</p>
<p>-a multi-database cluster system, WorldDatabase DB, providing infinitely scalable secure encrypted data storage</p>
<p>-a World Database DB underlying architecture support system, including a block storage system and a distributed file system
an attribute-based cryptographic authenticated access system consisting of a multi-node consensus, WorldDatabase ABE, the database's access control gateway</p>
<p>-a World DatabaseTPA Chain (WorkChain3), a data integrity verification organisation consisting of multiple verifier nodes</p>
<p>-An adaptive probe system, World Database Agent, providing in-memory data storage, performance monitoring, security monitoring and Metrics data upload capabilities</p>
<p>The key feature of World Database, and where it excels over IPFS, is the proof-of-ownership validation mechanism for data. Any storage project must theoretically provide a proof-of-hold mechanism, and with any implementable proof mechanism, there are bound to be challengers and provers. In existing storage projects, Sia and Storj both choose to have the user as the challenger, which requires the user to either keep a copy of the file itself, or to have a copy of the file for a specific period of time, a mechanism that can only be used to implement a network drive, but not a cloud storage or cloud database. This introduces a lot of complex logic, such as zero-knowledge proofs and so on. For our purposes, we need the chain node to act as the challenge party, which then introduces two properties.</p>
<p>1 Our validation subchain nodes need to be sharding, i.e. not all nodes (thousands) can validate a file at the same time, which is a huge waste of resources. At the same time, the validation nodes need to have a strong consistent consensus on the validation results, i.e., a consensus is formed through BFT. This then dictates that we need to have a sharding chain and that the consensus mechanism within sharding is BFT, i.e. strong consensus.</p>
<p>2 We need a separate chain to implement attribute-based encryption and access control over the entire pool of back-end storage and database resources. Typically, attribute-based encryption is based on a trusted cryptographic authority, and instead of a trusted authority, we use a chain and multiple authorities, which requires the introduction of the validator role and BFT consensus.</p>
<p>3 We need a chain to form a consensus on the joining of database nodes and the taking offline of database nodes, the consensus algorithm is also BFT. the nodes of this chain and the database nodes are the same runtime and need the protection of TEE and SGX.</p>
<p>4 We need a chain to count user requests to the database system and this chain is a high speed chain. So, the requirements now proposed are: 1 Sharding 2 High-speed sub-chains 3 Isomorphic validation mechanisms such as BFT 4 Inter-chain communication When designing the data system, we use the technology of database clustering to provide services to decentralised applications in order to ensure availability, performance and scalability of the services. Clustering is a fundamental concept in World Database databases, where data is always replicated within a database cluster and does not cross clusters when providing services. In addition, clustering technology allows the load to be relatively balanced across all devices.</p>
<p>In order to maximise the storage capacity of each device and to maximise the overall performance of the storage system, World Database distributes data fairly according to the capacity and bandwidth of the devices. Furthermore, as new nodes are added to the system from time to time, as well as the removal of unqualified devices, or the failure of devices at certain nodes, it is necessary to redistribute data fairly in order to maximise the performance of the storage system. Some applications of the World Database system may run 24 hours a day, and migrating large amounts of data will consume large amounts of bandwidth, degrading the quality of service of the World Database system to the application, and even affecting the availability of the system as a whole. In order not to affect the system's storage services, World Database's algorithm ensures that the amount of data redistributed is as small as possible. Thus, the data layout algorithm of the database system can dynamically adapt to changes in storage size, migrating as little data as possible as the system size changes. It also ensures that the layout algorithm is able to calculate the location of a particular piece of data using little time and space information.</p>
<p>The CCHDP (clustering-based and consistent hashing-aware data placement) algorithm used by World Database can fairly distribute data in a heterogeneous collection of devices according to the weight of the devices, adapts to changes in storage size, migrates the least amount of data when storage size CCHDP is an algorithm that combines clustering and consistent hashing techniques.</p>

              </div>
				
				
            </div>
        </div>
		
		
		
        <div class="wenz-right" v-show="docselectIx == 7">
            <div style="margin-left: 10px;">
                <div class="right-title flex-l">Disclaimer</div>
				
<div class="markdown-body">
                <p>The technical documents illustrated in the World Database project are not intended for sale or a solicitation of bids for shares, securities or other regulated products of the relevant companies. This document cannot be used as a prospectus or any other form of standardized contractual document, nor does it constitute an offer or solicitation of investment advice for securities or any other regulated products in any jurisdiction.</p>
<p>This document does not constitute any sale, subscription or invitation to others to purchase and subscribe to any securities, and form of contact, contract or promise based on it.</p>
<p>No information or analysis presented in this document constitutes a recommendation to engage in any decision to invest in tokens, and no specific recommendation with a predisposition to do so will be made.</p>
<p>The World Database Foundation is not responsible for any direct or indirect loss of assets resulting from participation in this project. This document may be modified or replaced at any time, however, we are under no obligation to update this version of the white paper or provide readers with access to additional information. The World Database Foundation holds the right of final interpretation of this document.</p>

              </div>
				
				
            </div>
        </div>
		
		
    </div>
{/block}
{block name="footer"}
</div>
    <div class="footer-bottom-wrap">
        <div class="bottom-bubu flex-center">© 2020 WorldDb Project. All Rights Reserved.</div>
		<div class="bottom-bubu flex-center">Service Support : Worlddatabase2019@gmail.com</div>	
    </div>


    <script src="/static/assets/js/vue.js"></script>
    <script type="text/javascript">
        init_bui();
        function init_bui() {
            var _vue = new Vue({
                el: '#app',
                data: {
                    userIx: 0,
                    docselectIx: 0,
					selextIx: null,
					langState: false,
					kgStatus: false
                },
                created() {

                },
                mounted() {
                },
                methods: {
                    sumbit(){
                        //this.docselectIx = this.userIx == 0 ? 1 : 2;
                    },
                },
            })
        }
    </script>
</html>
{/block}